Modular Personal Network Systems and Methods

ABSTRACT

Modular personal networks (MPNs) are disclosed that include multiple devices that may be worn, carried, or used in close proximity to a user. The devices communicate wirelessly. Devices include security circuitry that prevents them from being used in a different MPN once the user has configured them. Devices not designed for use within an MPN can be included in the network using a bridge device. Devices can be integrated into items of jewelry, such as earrings, rings, pendants, and bracelets. One item of jewelry, such as a bracelet, can support multiple replaceable modules with variable functions. Functions of the MPN can include communications, entertainment, medical monitoring, sports monitoring, personal organization, and games. Multiple users each with his or her own MPN can use them to collaborate in creation of music. An MPN can be used for mobile recognition and logging of wildlife.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/785,667, filed Mar. 5, 2013, which is a continuation of U.S.application Ser. No. 10/764,287, filed Jan. 23, 2004, which claims thebenefit of U.S. Provisional App. No. 60/442,418, filed Jan. 25, 2003,which are hereby incorporated by reference herein in their entireties.U.S. application Ser. No. 10/764,287 is also a continuation-in-part ofU.S. application Ser. No. 10/645,713, filed Aug. 20, 2003, which is acontinuation of International App. No. PCT/US02/04947, filed Feb. 20,2002, which claims the benefit of U.S. Provisional App. No. 60/270,400,filed Feb. 20, 2001, which are also hereby incorporated by referenceherein in their entireties.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to modular personal network systems andmethods, and, in particular, to wireless networks of individualcomponents that can be easily added to or removed from a network tochange the network's functions, and in which the individual componentsare worn, carried, or used on or about the person of the user.

2. Background Art

A Modular Personal Network, or MPN, is a network of personal devices,each of which is designed to optimally perform a specific task, creatinga system that is greater than the sum of its parts. Examples of MPNs areillustratively disclosed in WO 02/067449, “Modular Personal NetworkSystems and Methods”, to Ellis et al, which is hereby incorporated byreference herein in its entirety.

A number of improvements to the MPN are desired. MPN users need animproved method of providing security in the MPN and its components, sothat individual components cannot be used in an MPN other than the onefor which they were configured.

MPN users may have existing devices, such as digital cameras, mobiletelephones, MP3 players, and personal digital assistants that were notdesigned for use within an MPN. Such users may need a device that canprovide a communications bridge between an MPN and such a preexistingdevice.

Wildlife enthusiast have a need for an improved system to recognize andlog wildlife animal and plant sightings, as well as to upload the logsto a personal computer and to compare them with the logs of otherenthusiasts.

Musicians may desire a personal network of individual devices to use inthe creation of music. Further, some musicians desire a system thatfacilitates musical collaborations.

Some MPN users may be interested in individual network components thatcan be worn unobtrusively, and which may have a pleasing appearance.Such users may desire an MPN individual network component (INC) that canfunctions as an item of jewelry. Some of these users may be interestedin modular jewelry systems, in which individual modules, such as linksin a bracelet, may be added at any time. These users may be interestedin a modular system that provides added electronic functions with theaddition of each new jewelry module into the system.

BRIEF SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, modularpersonal networks and methods are provided.

MPN concepts may be illustratively explained based on the parts of itsname:

Modular: Each device provides one or more functions to the network. Anew device can be added at any time, increasing the capabilities of thesystem, for example, without losing anything that already is supported.A single device (e.g., any single device) can be removed, for example,at any time, resulting in a system that can perform without that device(e.g., one less function), but which still works well as a system.

Individual devices can be swapped out, for example, at any time. Forexample, a user may decide that a green display goes better with today'soutfit than yesterday's blue display. The new display can be substitutedwithout impacting any of the other devices, and without reducing any ofthe functions of the system.

The network protocols may, for example, be “open”, which means that newdevices with new capabilities can be designed at any time and broughtinto the network. This approach allows the network to perform functionsthat were not imagined at the time it was originally created.

Personal: The devices are small and designed to be carried or worn by auser. As such, they may be worn at the waist, around the wrist, mountedto an item of clothing, carried in a pocket or purse, or mounted to apiece of the user's personal equipment, etc. The network is preferablyunobtrusive and may not even be noticed by other individuals. The entirenetwork is preferably about the same size as the user's “personalspace”. Each device may, if desired, be further personalized, so that itonly functions in its user's network.

The MPN can also be considered personal because it can provide exactlythe design and functions that the user wants at any particular time. Anadvantage of this technique is that users no longer have to live withthe limited set of functions that some manufacturer decides is the bestcombination. If the user needs something new, he can preferably just getthe new component and add it to the network. If the user no longer wantsa particular feature, components can preferably be removed one at atime. If the user wants to mix and match, the combinations can beunlimited. If desired, in some instances, one or more components thatare not “personal” may be added to an MPN.

Network: The devices in the MPN preferably communicate using alow-power, short-range wireless network, for example at a 2.4 GHz radiofrequency. Each device preferably has a range of a few meters formessages to and from other devices in the network. Any device canpreferably talk to any other device in the MPN, using, for example, astandard protocol.

An advantage of the MPN can be the ability for the user to add or removeindividual network components (INCs) while maintaining the integrity ofthe network. If the INC is of a known type and the desired new functionis already defined, a new INC can preferably be added on the fly, simplyby bringing into proximity of the network. If it's a new type of INC, orif a new function is desired from an INC already in the MPN, the newfunctionality can preferably be downloaded into the MPN.

There are two types of MPN that are illustratively described herein. Thefirst type has a control unit as one of the INCs. The control unit isthe hub of the MPN. It communicates with all of the other INCs andcoordinates the functions of the network. The second type of MPN hasdistributed control. With distributed control, each of the INCs providesits own control, and all INCs operate as peers.

The user's PC can be a base (e.g., the only base) from which the userconfigures and manages the MPN. There may be an application that runs onthe PC, and which controls the functions of the MPN. If there is acontrol unit, the PC may communicate only with it. The PC mightalternatively communicate instructions to all of the INCs.

If the PC has a wireless transceiver card, it can communicate with MPNINCs using the INCs' wireless network (effectively becoming anotherdevice in the MPN). If desired, the INC may have a wired port, such as aUSB port, which can be connected to the PC. Or, the PC can have adocking station into which the INC can be connected directly. The userconnects the PC to the INC and can run the MPN PC application wheneverhe or she wants to control the MPN.

Some types of communication that can take place between the PC and theMPN INC may, for example, include:

The PC can download a new driver into a control unit to control a newtype of INC.

The PC can download a new software module into the control unit tosupport a new function using existing INCs.

The PC can download new software into any INC to control its functions.

The PC can download configuration parameters, or the current time, intothe Control Unit or any other INC.

The PC can download music or other media into the control unit forplayback.

The PC can download any other type of data into an INC.

The PC can upload collected data from the control unit or other INC.

The MPN PC application supports plug-ins to handle unanticipated typesof INCs. For example, the application itself can handle genericdownloading of software and data, and the plug-in can handle specificnew functions. This may include configuration of specific INCparameters, uploading of new types of data, displaying, processing, andstoring uploaded data, or any other functions specific to the new INC.

MPN devices (e.g., all MPN devices) preferably use a standard protocolfor messages within the network. This protocol may be built on top of anindustry standard wireless protocol, such as IEEE 802.15. The vastmajority of the communication to and from any INC is with other INCs inthe same network, and the protocol is preferably optimized for this.

Preferably every MPN is assigned an identifier that is unique to thatMPN, and each message within that MPN is preferably tagged with thatidentifier. This allows INCs to determine whether a message it receivesoriginated within its own MPN, or whether it has received a straymessage from another MPN.

Preferably, each INC in the MPN has an identifier that is unique withinthat network. Individual INCs (e.g., each INC) may maintain a table ofother INCs in the network that it may send messages to or receivemessages from. A standard table of INC types, manufacturers, andcapabilities may be built into all INCs, and the table may be augmentedwith data downloaded from the PC as new types of INCs are supported.

INCs of the same type may use the same protocol messages. For example,two different types of display INCs built by different manufacturerswould accept and process the same types of messages to displayinformation graphically. Standard messages are also defined to query thespecific capabilities of an INC. For example, a control unit might querya display INC to determine its pixel resolution, availability of colors,and other features.

When a user creates a new MPN (by buying the first component or “starterkit”) the MPN will preferably be programmed with a unique MPN lock. Forexample, the package with the MPN application to be loaded on the PCwould include a “lock number,” a unique sequence of letters and numbers.The first time the user connects the INC to the PC, the applicationwould prompt for the lock, and for a new password from the user. Theapplication would then download the lock into the INC. The INC wouldstore the encrypted lock in a secure memory on the INC.

As the user adds new INCs to the network, each would preferably beprogrammed with the same lock. If desired, the application could storethe lock on the PC, and only require the user to enter the password (andnot the lock) each time a new INC is added to the MPN.

Once in an INC's memory, the lock value is preferably stored in securememory and cannot be retrieved. If the user wishes to remove an INC fromthe network and give it to someone else to install in another network,the PC application can for example allow the user to delete the lockfrom the INC by typing in the original lock value and password.

If the user loses the original lock value or password, the INCs canstill be used together. However, in some embodiments, new INCs cannot beadded to the network because of the lost lock value or password. In suchinstances, an authorized repair facility may have a method to clear thelock from secure memory, so that the user could add the INCs into a newMPN with a new lock value. The clearing of secure memory may be done inperson, by sending the device(s) to the repair facility, or over theInternet using security controls such as passwords, PINs, etc.

Each time an INC is brought into the MPN, the other INCs (e.g., one ormore of them) may query it to ensure the locks match. The lock value maybe sent in an encrypted format so that it cannot be stolen. In anothertechnique, a “key” value can be sent from the new INC, and the otherINCs can use the key to try to open the lock. The required key value maybe varied based on the time, the sending or receiving INC, or othercriteria, so that a stolen key cannot be used at a later time.

If desired, the lock value can also be used to derive the unique MPNidentifier, used to tag messages sent between INCs in the network.

Each INC in the MPN is preferably individually powered. The battery maybe a single-use, long-life power source. Rechargeable batteries may alsobe used, which may be automatically recharged when the user plugs theINC into the PC or the docking station at the PC.

Each INC preferably includes power-monitoring circuitry. Thecommunication protocol may include messages to report low powerconditions. The complete loss of power in an INC (e.g., any INC) canpreferably be predicted before it happens and reported to the user. Ifan INC loses its power, it will preferably be handled gracefully, forexample, similar to the removal of the INC from the network.

The MPN preferably includes a global power-off and power-on feature. Forexample, when an airline passenger is using electronic devices he mustshut all of them off as the airplane approaches landing. The MPN userwill turn off one INC. That INC will broadcast a message to all of theother INCs in the MPN. Each INC will then store any temporary statusinformation, stop all wireless transmissions, and go into a low powerconsumption state. All of the INCs will remain in this state until theuser turns one of the INCs (e.g., the first INC) back on. This INC willbroadcast a resume message, and all of the INCs in the MPN will resumenormal functions. In this example, if desired, a complete shutdown ofINCs may also be applied.

Some INCs and features may also have timeout features, in which theyautomatically go into a low power consumption state after a definedperiod of inactivity.

The functions of every MPN INC preferably include a number of standardfunctions. The use of a standard “reference design” with standardcomponents can significantly reduce the cost of every INC. Anapplication specific integrated circuit (ASIC) designed specifically toencapsulate these common functions can, for example, allow a compact,low-cost design of new INCs. It can also help to ensure compatibilitybetween INCs, and to create a common set of user expectations.

Some of the common functions that may be encapsulated, for example,include:

Wireless transmission and reception

Low-level and high-level protocols

Protocol extensions capability (memory and processor, for example)

Power management

Secure memory and lock/key handling

Standard device types, manufacturers, and capabilities

Some capabilities may be used in many but not all INCs. Thesecapabilities would also benefit from reference designs and standardcomponents. These capabilities, for example, include:

PC communication protocol

Extended processor and memory for more advanced functions

There may be several types of INCs that will be present in a largepercentage of MPNs. These, for example, may include:

Control Unit: Can be considered the general-purpose processor forcontrolling the functions of the MPN. It preferably includes a processorand memory. The memory can be used for downloading software modules tocontrol the other INCs and performing specific functions. It may also beused for storing digital music, or other types of media, to play backfor the user, or which the user has captured. It may also be used forcollecting data from the other INCs. The control unit may be worn on thewaist, worn on a wristband, or carried in a pocket or purse, etc. Memorycan be of any type or combination of types, such as RAM, hard disk,CD-ROM, mini-disk, flash memory, and may be permanent or removable.

Display: The display will typically be a general-purpose graphicaldisplay device, such as an LCD. It may, for example, be worn on thewrist.

Audio Output: An audio output (such as headphones) may often beincluded.

User Input: User inputs (e.g., buttons) may be included separatelyand/or on any of the other INCs, such as the control unit or display.There may also be separate user controls to support some features. Thesecould include microphone input, pen-based input, a keyboard, or anyother appropriate portable input device.

Phone: A mobile phone or other communications device can be included asan INC in the network. The actual INC may be minimal, as the phonefeatures may use the functions of the control unit, display, audiooutput, and user control, rather than duplicating those functions.

Other common INCs, for example, include a digital camera. GPS receiver,and a heart rate monitor.

There may also be common collections of functions into single INC. Forexample, there may be combination control/display/user input INCs.

If the user has an existing device, such as a mobile phone, personaldigital assistant (PDA). MP3 player, or digital camera, that is notMPN-ready, that device may still be incorporated into the MPN. One ofthe MPN INCs, for example the control unit, may have a USB port or othertype of connector to interface with the existing device, and it may beable to accept downloaded software to interact with the existing device.

For example, the existing device may be an MP3 player or a digitalcamera with a USB port, originally designed to interface with a PC. Thecontrol unit may have a USB port. Software downloaded into the controlunit may enable it to access the features of the existing device overthe USB port, for example to download music into the MP3 player or toupload digital photographs from the digital camera.

If the existing device is a mobile telephone, the control unit may havea port that allows access to the accessory port on the phone to accessits functions, for example to send audio to the phone, to get audio fromthe phone, to dial, or to perform other functions. If the existingdevice is a PDA, the control unit may have a port and software thatallow access to functions of the PDA, using the PDA synchronization portthat was originally designed to interface with a personal computer.

The control unit or other MPN device that is connected with the existingdevice may use its wireless transceiver to make the functions of theexisting device available to other INCs in the MPN.

With the use of a standard design and a public protocol, anymanufacturer can build INCs to be used in any MPN. There would likely bea certification process to ensure that new INCs are truly compatible andinteroperable.

Establishing interoperability allows a user to buy any combination ofINCs of different types from different manufacturers, and count on themto work together correctly. A user can even have INCs of the same typefrom different manufacturers, and use them at different times. Thiswould allow a user to shop for the best bargain for any INC or set ofINCs.

If an INC fails, it can preferably be replaced with the same type ofINC, or with a different INC providing similar capabilities.

When the MPN is connected to a PC, the MPN can preferably communicatewith the outside world, using the PC's Internet connection (e.g., underthe control of the application on the PC). This, for example, allows anumber of types of interaction:

The PC can download updated software to control INCs or provide newfeatures.

Control commands or configuration parameters can be provided for the MPNfrom a doctor, coach, therapist, etc.

A service technician can diagnose problems in the MPN. The servicetechnician can also remotely clear the secure memory in an INC.

Data from the MPN can be shared with other computers on the Internet.

Two MPN users can share data between their networks.

If desired, sharing of data can also happen directly when two MPN usersare in close proximity. For example, by extracting the unique MPNidentifier from a message sent by an INC of another MPN, a message canbe addressed back to an INC of the other MPN. This can allow featuressuch as multi-player games and competitions, sharing of personal data,sharing of media files, sharing of software, etc.

An MPN can include a communication INC, such as a mobile phone, as oneof the INCs in the network.

MPN devices may be packaged in a number of ways, including for example:

Starter kit: This kit includes the MPN PC application, a security lockvalue, and some basic INCs (control unit, display, etc.) It may includea link to a website to find updated plug-ins, drivers, device lists,etc. There may also be coupons for other MPN products offered by thesame manufacturer.

Device kit: This kit includes a specific INC. If appropriate, it mayalso include a plug-in and driver to control and configure the INC.

Feature kit: This kit includes the items necessary to implement aspecific feature. It may include one or more INCs. It may include aplug-in for the feature. It may include one or more updated drivers. Itmay also include web links to get updates.

Multi-purpose device: Some manufacturers may choose to create singleINCs capable of performing several functions.

Adapter kit: This kit includes the items necessary to adapt a non-MPNdevice to be used in an MPN. It may include a specialized control unit,an adapter cable, a software plug-in, downloadable software, or otherappropriate items.

One method of making a wearable INC is to incorporate it into an item ofjewelry, so that it provides an aesthetically pleasing form when worn bya user. It may not even be obvious to anybody other than the wearer thatthe item is anything other than pure jewelry.

For example, an INC can be incorporated into an earring or otherwisedesigned to be worn in a pierced body part. An earring INC may include,for example, a wireless receiver and a speaker. This would allow otherINCs to send audio content to be played in close proximity to the user'sear, at a low and unobtrusive volume. Another example of an earring INCis to include an antenna for a GPS receiver or a mobile telephone. Thereceived signal may be remodulated and sent to another INC forprocessing.

An INC may be worn as a pendant around the neck. The pendant may be anyappropriate INC, such as a control unit, a display device, a user inputdevice, a GPS receiver, or may provide any other suitable function orcombination of functions.

An INC may be worn as a ring or may be included as part of a ring. Thering INC may include a user input device such as pushbutton or amicrophone. The ring INC may include any other type of device such as adigital camera, a pulse oximeter, a blood pressure sensor, a simpledisplay device, etc.

An INC incorporated into any number of jewelry items including, but notlimited to: a brooch, cufflinks, tie tack, tuxedo studs, barrette orother hair accessory. An INC may be included in eyeglass temples (forexample as an antenna or a speaker).

Another type of jewelry that may include one or more INCs is the modularjewelry system, such as a modular bracelet or charm bracelet. A modularbracelet is designed to allow the user to add or remove individual linksat any time. A charm bracelet allows individual charms to be added orremoved at any time. Any of the modular links or charms may include awireless transceiver and provide the functions of any appropriate INC.Each new modular link or charm may add similar capabilities, such as anadditional amount of memory, or they may each add a different type ofcapability. For example, one charm may include a processor to act as acontrol unit, a second charm may provide memory, a third charm mayprovide an input sensor (such as a temperature sensor), and a fourthcharm may be a user input device.

If multiple modules are added to a modular jewelry system, they may actas a single INC. For example, one of the jewelry modules may provide thewireless transceiver that is used by all of the other jewelry modules.Or, the base system without any added jewelry modules may include thewireless transceiver, power source, processor, memory, and any otherelectronics required to interact within the MPN, and each added jewelrymodule may include only the electronics required to add a specific newfunction. The modular jewelry system itself may act as thecommunications bus for transferring data among the jewelry modules inthe system.

In fact, the modular jewelry system may be capable of providingfunctionality without any other INCs. In this case, the system canprovide any new functions simply by attaching a new jewelry module tothe base system.

A number of functions can be supported even with the most basic MPNhardware. These, for example, include:

Time functions, such as a wristwatch

Personal organizer functions, such as appointment notification andcontact information (synchronized with data on the user's PC)

Music playback

Personal information exchange with another MPN

Games (single user or with another MPN)

The MPN can provide a mobile wildlife recognition and logging system.Prior to an excursion, the user can download into an INC in the MPN alibrary of information about flora and fauna of a particular region.This can include photos, audio sample of animal calls, information abouthabits and territories, and text descriptions. If desired, the librarycan be loaded in on a mini-disk or other removable data storage device.

During the excursion, the user sees an animal or plant of interest, andtakes a picture using a digital camera INC connected to the MPN. Anaudio sample can also be taken using an INC. The MPN can use the image,the audio sample, location information, time of day, current weatherconditions, or other factors to determine one or more likely matchesfrom the wildlife library. These likely matches are presented to theuser on a display INC, and the user can make the final determination.The user uses the images, audio samples, and other data from thepossible matches to make the determination, or can narrow it down to themost likely matches. The MPN keeps a log of what wildlife was seen whenand where, which can be reviewed on the MPN, and can be uploaded laterto the PC.

This feature may be of particular interest to birdwatchers, who can usethis system to keep their bird watching diaries electronically. Thesystem may support comparison of logged sightings between multiplebirdwatchers.

The MPN can provide features for musicians. For example, a musician canhave INCs for microphones and speakers, an INC to store music, an INC toconvert stored music from one format (e.g., Midi) to audio for output,an INC to perform audio processing and special effects, an INC to mixmultiple inputs, and an INC to display sheet music.

Multiple musicians, each with an MPN, can use features of the MPN toplay together. For example, messages sent between the systems cancoordinate the timing and the playing of a single piece of music.Multiple audio inputs can be received by components of the MPNs andmixed and stored into a single INC. The recorded music can be uploadedto a PC or other music processing system for later processing.

BRIEF DESCRIPTION OF THE FIGURES

Further features of our invention, its nature and various advantageswill become more apparent upon consideration of the following detaileddescription, taken in conjunction with the accompanying drawings, inwhich like reference characters refer to like parts throughout, and inwhich:

FIG. 1 is a block diagram of two INCs within an MPN that provide secureprocessing;

FIG. 2 is a block diagram of a personal computer providing configurationof security functions within an INC;

FIG. 3 is a flowchart of an illustrative process showing how securitycan be provided within an MPN;

FIG. 4 is a flowchart of an illustrative process for providing securitymaintenance functions for an MPN;

FIG. 5 is a block diagram of the functions provided by thesecurity-processing circuitry within an INC;

FIG. 6 is a block diagram of an INC;

FIG. 7 is a block diagram of the power module of an INC;

FIG. 8 is a block diagram of an application-specific integrated circuitthat may be used within an INC;

FIG. 9 is a block diagram of an MPN with an INC that has a hard-wiredconnection to a non-MPN device;

FIGS. 10A through 10E are block diagrams of INCs that interface withnon-MPN devices;

FIG. 11 is a flowchart of an illustrative process for providing aninterface to a non-MPN device within an MPN;

FIGS. 12 and 13 are block diagrams of illustrative MPNs;

FIG. 14 is a flowchart of an illustrative process for providing variousMPN product packages;

FIG. 15 is a block diagram of an illustrative music collaborationsystem;

FIG. 16 is a block diagram of an illustrative wildlife recognition andlogging system;

FIG. 17 is a flowchart of an illustrative process for providing a mobilewildlife recognition and logging system;

FIG. 18 is a flowchart of an illustrative process for allowingindividual network components to be worn or carried;

FIG. 19 is a flowchart of an illustrative process for allowingindividual network components to be incorporated into items of jewelry;

FIG. 20 shows an example of an MPN including several INCs incorporatedinto items of jewelry;

FIG. 21 is a block diagram of a modular jewelry system; and

FIG. 22 is a flowchart of an illustrative process for providing amodular jewelry system.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 shows illustrative modular personal network (MPN) 100. MPN 100includes individual network component (INC) 120 and INC 140. Each INCincludes a wireless transceiver, such as wireless transceiver 127 andwireless transceiver 147, or in some cases a wireless receiver orwireless transmitter. The INCs communicate over wireless path 160.

Each INC 120 and 140 has secure memory 121 and 141, in which a lockvalue 122 and 142 is stored. Each INC also includes security-processingcircuitry 123 and 143. The security-processing circuitry accesses thelock value from secure memory over secure path 126 or 146. The securememory may be designed so that stored information, such as the lockvalue, cannot be retrieved except by the security-processing circuitry,and may require the use of an access code. The security-processingcircuitry may use the retrieved lock value to determine the MPNidentifier 124 and 144 of the INC. The MPN identifier may be used to tagmessages sent between INCs, so that each INC only responds to messagesthat originated from another INC in the same MPN.

When an INC, such as INC 120, is added to an MPN, it may send a keyvalue 161 to INC 140. Security-processing circuitry 143 in INC 140 mayuse received key value 161 and lock value 142 to determine whether INC120 is a legitimate component in MPN 100.

FIG. 2 shows how personal computer (PC) 210 may communicate with INC 140over communications path 220. INC 140 may have PC connection 230, whichmay be a wired connection such as a serial port or USB port, may be thesame as wireless transceiver 147, or may be any other suitable wired orwireless connection. For example, PC 210 may download a driver into INC140 to control another INC. As another example, PC 210 may download anew software module into INC 140 to supplement or replace existingsoftware, to add a new function to INC 140 or to modify an existingfunction in INC 140. As another example, PC 210 may downloadconfiguration parameters to INC 140. As another example, PC 210 may sendthe current time to INC 140. As another example, PC 210 may downloaddigital audio or other media (such as images and video) to INC 140. Asanother example, PC 210 may download any other type of data to INC 140.As another example, PC 210 may upload media data that may have beencaptured by INC 140, such as audio, video or still images. As anotherexample, PC 210 may upload any other type of data that may have beencollected by INC 140, such as location data, speed data, heart ratedata, or medical data. As another example, PC 210 may allow anothercomputer to access data on INC 140 or download data to INC 140, using anetwork such as the Internet. This may include allowing a doctor,therapist, or coach to download instructions to INC 140 and to uploaddata from INC 140. It may also include allowing a service technician toremotely access INC 140 for configuration, upgrade, troubleshooting, andother maintenance functions. A user may also be able to access data andsoftware upgrades on the Internet and download them into INC 140 from PC210.

As another example, PC 210 may perform security functions with INC 140.This is illustrated by flowchart 300 in FIG. 3. Some steps in flowchart300 may be optional or may be performed in a different order. In step310, a lock value may be provided to a user. For example, the user maypurchase an MPN starter kit. The starter kit may include one or moreINCs, one of which may be a control unit. The starter kit may alsoinclude other items, such as PC software that may be used to interfacewith the INCs of the MPN. If the INCs have a wired connection to the PC,the starter kit may include a cable to make the connection, such as aserial cable or a USB cable. The starter kit may also include a lockvalue. The lock value may be unique to the starter kit—each starter kitmay have a different lock value. If desired, the starter kit may notinclude any INCs—they may be sold separately.

In step 315, the user may configure an INC, such as INC 140 using PC210. INC 140 may have been purchased as part of a starter kit, or it mayhave been purchased separately. The user may use a cable that waspurchased with the INC, with the starter kit, or purchased separately.If the connection between PC 210 and INC 140 is wireless, the user mayput INC 140 into proximity of PC 210. The user may load software onto PC210 that was, for example, purchased with INC 140 or with the starterkit, and the user may use the loaded software to configure INC 140. Ifdesired, the user may load a plug-in that was purchased with INC 140 toaugment software that was purchased with the starter kit. The user maythen use the software loaded on PC 210 to load software andconfiguration data into INC 140. One of the types of configuration datathat may be loaded into INC 140 is the lock value. This may be the lockvalue that was purchased as part of the starter kit. In someembodiments, rather than loading the lock value itself, a value derivedfrom the lock value using any suitable algorithm may be loaded. Thesoftware loaded onto PC 210 may prompt the user to enter the lock value.It may also prompt the user for a password. The first time the userenters the lock value, the user may be prompted to create a new passwordand to confirm it. The software may store the lock value and thepassword, in an encrypted format, on PC 210's disk drive or otherstorage device. PC 210 may send, in step 320, the lock value, or a valuederived from the lock value, to INC 140 over communication path 220.

In step 330, the lock value or the value derived from the lock value maybe stored in secure memory 141 in INC 140. The lock value may betransmitted in encrypted format, it may be encrypted bysecurity-processing circuitry 143, or it may be stored in unencryptedformat.

In step 335, the user may configure a second INC, such as INC 120 ofFIG. 1. INC 120 may have been purchased along with INC 140, may havebeen purchased as part of a starter kit or other package, or may havebeen purchased separately. INC 120 may be connected to PC 210 of FIG. 2using the same means as was used to connect INC 140. INC 140 may beconfigured using the same software on PC 210, different software on PC210, or using the same software and with a plug-in that was purchasedalong with INC 120. Configuration of INC 120 may include downloadingsoftware to INC 120. It may include downloading software to one or moreadditional INCs, such as INC 140, which may be a control unit.Configuration may also include downloading configuration settings to INC120, INC 140, or any other INCs that are included in the same MPN.

As part of the configuration of INC 120, the lock value may bedownloaded into INC 120, in step 340. The user may be prompted for thepassword to enable the download of the lock value (or the value derivedfrom the lock value). If desired, the lock value may have beenpreviously stored on PC 210, so that the user does not have to reenterit when configuring new INCs for the same MPN. If desired, the softwarerunning on PC 210 may track the lock values associated with multipleMPNs, and may allow the user to name each MPN so that it can be laterreferred to without having to remember the individual lock values foreach.

After the lock value or derived value is sent to INC 120 overcommunication path 220, it may be stored in secure memory 121, in step350. The lock value may be transmitted in encrypted format, it may beencrypted by security-processing circuitry 123, or it may be stored inunencrypted format.

The user may, at some point after configuring INC 140, be using it aspart of MPN 100. The user may wish to begin to use INC 120 as part ofMPN 100, in step 360. When INC 120 is brought into proximity of INC 140,there may be a check for a match between the components. INC 140 maysend a query to INC 120 for identifying information over communicationpath 160, in step 370. INC 120 may send identifying information to INC140 over communication path 160. The identifying information may includea unique MPN identifier. The MPN identifier may be stored in the INC, orit may be derived from the lock value. The identifying information mayinclude the lock value. However, sending the lock value may not besecure. The identifying information may include a key value 161. Onreceipt of the key value, INC 140 may use a security algorithm to checkfor a match with the lock value stored in secure memory 141, in step375.

The key value may be fixed for each lock value, or for each combinationof lock value and INC. Alternatively, it may be varied over time so thata stolen key value cannot be used at a later time.

If there is no match, then in step 380 INC 140 may disallow the use ofINC 120 in MPN 100. Other types of communications may still be allowedbetween INC 120 and INC 140, where the communications are of typesappropriate between different users. This may include exchange of data,playing games, etc.

If there is a match, then in step 390 INC 140 may allow the use of INC120 in MPN 100. This may include INC 140, and possibly other INCs in MPN100, recording identifying information about INC 120 in local memory, sothat subsequent communication may proceed without further query. Ifdesired, INC 120 may also store information about INC 140 and other INCsin MPN 100.

FIG. 4 shows a flowchart 400 for providing security maintenancefunctions for the MPN. Some steps in flowchart 400 are optional and thesteps may be performed in any suitable order. In step 410, the systemmay disallow the retrieval of the lock value. This may include thestoring of the lock value in encrypted format within PC 210, within eachINC, and while it is being transmitted between the PC and variouscomponents in the MPN.

In step 420, the system may allow a lock value to be deleted from anINC. For example, a user may wish to remove an INC from his or her MPNand give the INC to someone else for use in another MPN. The softwareloaded on PC 210 may request the password from the user, and send acommand to the INC to clear the lock value from its secure memory.

The user may at some point lose or forget the password and/or the lockvalue, or wish to change the password. If the user loses the lock value,they can continue to add and remove INCs from the MPN using thepassword. If the user forgets the password, the software may allow theuser to create a new password by entering the lock value in step 430. Ifthe user wishes to change the password and remembers the old password,the software may allow the user to enter a new password by firstentering the old one in step 440. If the user loses both the lock valueand the password, existing INCs can continue to be used in the MPN, butnew INCs cannot be added, and the INCs cannot be removed from the MPN tobe added to another MPN, in step 450. However, an authorized repairfacility may be able to delete the lock value from an INC, in step 460.For example, the user may deliver the INC to the repair facility, or itmay be performed over the Internet, with appropriate securityprecautions. Other techniques may also be used if desired.

FIG. 5 shows more detail of the functions that may be provided bysecurity-processing circuitry 543. In function 510, a lock value may bestored in secure memory 541 by security processing circuitry 543.Function 510 may provide the lock value in encrypted format as well asthe user-specified password, which may also be encrypted.Security-processing circuitry 543 may store the encrypted lock value andpassword. If the storage operation is successful, which will typicallybe true if there isn't already a lock value and password stored, it willreturn an indication of the successful completion of the operation. Ifthe storage operation is unsuccessful, for example if there is already alock value and password stored in secure memory 541, an indication ofthe failure of the operation may be returned.

In function 520, the password stored in secure memory may be changed.The new password value, which may be encrypted, may be provided, alongwith the encrypted lock value for confirmation. If the operation issuccessful. i.e. if the provided lock value correctly matches the lockvalue stored in secure memory 541, the new password may be stored intosecure memory 541, replacing the existing password. If the provided lockvalue does not match, an indication that the operation was unsuccessfulwill be returned.

In function 530, the password stored in secure memory may be changed.The new password value, which may be encrypted, may be provided, alongwith the old password value for confirmation, which may also beencrypted. If the operation is successful, i.e. if the provided oldpassword value correctly matches the password value stored in securememory 541, the new password may be stored into secure memory 541,replacing the existing password. If the provided old password value doesnot match, an indication that the operation was unsuccessful will bereturned.

In function 540, the lock value and password stored in secure memory maybe cleared. The password value, which may be encrypted, may be provided.If the operation is successful, i.e. if the provided password valuecorrectly matches the password value stored in secure memory 541, thepassword and lock value may be cleared from secure memory 541, allowingthe INC to be programmed with a new password and lock value. If theprovided password value does not match, an indication that the operationwas unsuccessful will be returned. If desired, this function may acceptthe lock value as a substitute for the password value, or it may requireboth the password and the lock value.

In function 550, a key value from another INC may be checked to see ifit matches the lock value stored in secure memory 541. The key value,along with any desired auxiliary data may be provided. Auxiliary datamay include, for example, the current date or time, the identifier ofthe other INC, the identifier of this INC, or any other suitablevalue(s). The security-processing circuitry 543 may use the provideddata along with the stored, encrypted lock value, to determine if thereis a match. If the provided key value does not match, an indication thatthe operation was unsuccessful will be returned. In one implementation,the security-processing circuitry 543 may use an asymmetric encryptionalgorithm, with the provided key as the public key, and the encryptedlock value using the private key.

In function 560, the security-processing circuitry 543 may return thepublic key value associated with its lock value. It may use providedauxiliary data, such as the current time or the INC's unique identifier,or any other suitable information. This function may also return aunique identifier for the MPN. It may also return a unique identifierfor the INC.

Security-processing circuitry 543 may also support a maintenancefunction 590 that can only be accessed by an authorized repair facilityto clear the lock value and password stored in secure memory 541. It mayrequire the presence of specific codes or signals that are onlyavailable at an authorized repair facility.

Security-processing circuitry 543 and secure memory 541 may be standardpart of the design of all MPNs. If desired, these circuits may beincorporated into an application-specific integrated circuit, to easedesign and reduce costs.

FIG. 6 shows a block diagram of INC 600. Wireless transceiver 610 mayinclude radio-frequency transmitting circuitry and radio-frequencyreceiving circuitry. These circuits may, for example, transmit andreceive signals at a 2.4 GHz radio frequency. It may also include anantenna. The receiving circuitry may include analog-to-digitalconversion circuitry. The transmitting circuitry may includedigital-to-analog conversion circuitry. Wireless transceiver 610 mayreceive data and commands from one or more INCs in the MPN and may senddata and commands to one or more INCs in the MPN. If desired, anddepending on the type of INC 600, wireless transceiver 610 may includeonly transmission circuits or only receiving circuits. Communicationprocessing module 615 may include circuitry to process the incoming andoutgoing data handled by wireless transceiver 610. It may supportlow-level and high-level protocols. If desired, different protocollevels may be handled in different modules. The MPN-specific protocollevel may operate on top of an industry-standard protocol, such as IEEE802.15. Communication processing module 615 may also include a log ofother INCs that are currently supported within the MPN. It may alsoinclude a table of standard INC device types, manufacturers, andcapabilities. Extensions to these tables may be downloaded usingwireless transceiver 610.

PC connection 620 may provide a connector for a cable that is used toconnect INC 600 to a personal computer. It may be, for example, a USB(universal serial bus) connector, allowing the user to connect the INCto a USB port on the PC. The connection may alternatively be any type ofwired or wireless connection, such as a serial port, an infraredconnection, or any other suitable type of connection. If desired,wireless transceiver 610 may be used to communicate with a radiofrequency port on a personal computer. If desired, some INCs may nothave PC connection 620.

Control circuitry 630 may include various control functions. Forexample, it may include processing capabilities and memory or anysuitable type. It may also communicate with, and route informationbetween, other modules in the INC, such as wireless receiver 610,communication processing module 615, PC connection 620, primary function640, security-processing circuitry 543, and power module 660.

Primary function 640 includes circuitry to supply the function that theINC provides to the MPN and to the user. This may include an inputfunction (such as a heart rate or other metabolic sensor, globalpositioning system receiver or other speed/distance/location sensor,microphone, still or motion digital camera, or user input device),output function (such as a device controller, display device, or audiooutput), communication device (such as a mobile telephone), processingdevice, memory device, or any other suitable function. If desired, INC600 may include multiple such functions.

Security processing circuitry 543 may provide authentication of incomingand outgoing messages and theft protection, as described previously withrespect to FIG. 5. Power module 660 provides electrical power for INC600, and is described more fully with respect to FIG. 7. Means to wearor carry 670 may provide an attachment or other physical means by whichthe user can wear or carry INC 600. This may include a wristband, awaistband, a headband, a clip, a hook and loop type fastener, or anyother appropriate attachment means. It may include the means to wear INC600 directly on the user's body, or to attach INC 600 to an item ofclothing worn by the user. If desired, means to wear or carry 670 may beomitted, if INC 600 is intended, for example, to be carried in a purseor pocket.

Packaging 680 provides for the external appearance and physicalcharacteristics of INC 600. Packaging 680 may provide for protectionfrom the environment. For example, INC 600 may be water resistant,waterproof, shock resistant, drop resistant, radiation hardened,jostle-resistant (e.g., able to be carried in a purse or pocket withoutinterfering with its functions), high or low temperature resistant, orotherwise designed to function well in less than ideal conditions. INC600 may be designed to be able to be seen easily in various conditions(such as low ambient light, low contrast, etc.), or it may be designedto be difficult to see or to blend in with its background. Packaging 680may also provide for the aesthetic appearance of INC 600. For example,it may incorporate specific designs, patterns, colors, materials,textures, weight or weight-distribution, etc. It may provide for aspecific density (for example, so that INC 600 will float in water orsink in water.) It may provide for ergonomic use of INC 600, forexample, making it easy to hold, to view, to operate, or otherwise use.

FIG. 7 shows more detail of power module 660. Power module 660 mayinclude battery 710. Battery 710 may be replaceable, or it may behardwired into INC 600. If it is hardwired, it may preferably berechargeable. Alternatively, it may be designed for long-life undertypical use. If battery 710 is replaceable, it may also be rechargeable.Power level detection circuitry 720 may detect the voltage or powerlevel generated by battery 710. It may predict the amount of timeremaining or estimate the percentage of battery life remaining. Powerstatus reporting module 730 may report the time or percentage of batterylife remaining. If desired, INC 600 may have a user output device, suchas a display or audio output, which can be used to report the batterystatus or alert the user when battery life is low. If desired, thebattery status can be sent by power status reporting module 730 toanother INC to be reported, using wireless transceiver 610. If desired,the battery status can be sent by power status reporting module 730 to apersonal computer to be reported, using PC connection 620. If desired,power module 660 may maintain in memory (for example memory included incontrol circuitry 630) a log of battery status over time, which can bereported to the user by any appropriate means.

If desired, power module 660 may include charging circuitry 740, tocharge battery 710 in place. For example, charging circuitry 740 mayinclude a solar powered charging circuit. If desired, charging circuitry740 may include circuitry to charge battery 710 using electric powerreceived on PC connection 620. For example, if PC connection 620 is aUSB connection, power from the USB connection may be routed to powermodule 660 to charge battery 710 while INC 600 is connected to apersonal computer. If desired, other charging means may be included. Forexample, charging circuitry 740 may receive power from a docking cradleinto which INC 600 may be inserted. If desired, such a docking cradlemay also provide PC connection 620.

Power control module 750 may control various power functions. Forexample, when power level detection circuitry 720 reports that thebattery is near the end of its life, power control module 750 mayinitiate a graceful shutdown of INC 600. This may include storing ofinterim data values, notifying other INCs in the MPN, and any othersuitable actions prior to removing power from INC 600. Power controlmodule 750 may also include a time-based sleep function. After a definedperiod of inactivity, power control module 750 may place INC 600 into alow-power consumption mode, by turning off some or all functions of INC600. Power control module 750 may also support a global power-off andglobal power-on feature. In this feature, the user turns off a singleINC, which sends commands to all other INCs in the MPN, directing themto turn themselves off (go into a low-power consumption mode). When theuser turns back on the single INC, it sends commands to the other INCsdirecting them to resume normal operations.

If desired, several of the functions of the INC may be integrated intoone or more application-specific integrated circuits (ASICs). This maysimplify the design and manufacture of different types of INCs, byproviding a drop-in module that provides many of the common functions.It may also reduce the cost of each INC, and may also provide forreduced size and power consumption. It may also help ensure consistencyin certain features of the INCs. FIG. 8 shows an example of how severalfunctions may be integrated into a single ASIC 800. In this example,ASIC 800 includes wireless transceiver 610, communication processingmodule 615. PC connection 620, control module 630, security-processingcircuitry 543, and power module 660. If desired, ASIC 800 may includeonly portions of some of these modules. Any suitable arrangement ofmodules into one or more ASICs may be used, but preferably each ASICshould be designed to be usable in multiple types of INCs.

Some users may wish to integrate existing, non-MPN devices into an MPN.For example, a user may have an existing mobile telephone, an existingpersonal digital assistant (PDA), an existing MP3 player, an existingdigital camera, or any other suitable personal electronic device. FIG. 9shows a block diagram of MPN 900 that integrates an existing non-MPNdevice 920.

INC 910 provides an interface to non-MPN device 920. INC 910 includessoftware 915, which may be downloaded from a personal computer. Software915 is configured to control and access the functions of non-MPN device920. If desired, INC 910 may also provide any other suitable function orfunctions. INC 910 accesses non-MPN device 920 over communication path930. Communication path 930 may be, for example, a USB connection, amobile phone accessory port, a PDA synchronization port, an infraredport, or any other suitable type of connection. INC 910 makes thefunctions and features of non-MPN device 920 available to other INCs inthe MPN, such as INC 940, over wireless communication path 950. Ineffect, non-MPN device 920 can be treated as an INC by the other INCs inthe MPN.

FIGS. 10A through 10E show block diagrams of example INCs that provideinterface to non-MPN devices. FIG. 10A shows INC 1010 that provides aninterface to non-MPN digital camera 1018 with a USB port. INC 1010includes USB port 1014, to which USB cable 1016 may be connected. Theother end of USB cable 1016 may be connected to digital camera 1018. Ifdesired, USB cable 1016 may be zero length, i.e. INC 1010 may connectdirectly to digital camera 1018. INC 1010 includes USB communicationsoftware 1013 that provides the USB protocols. If desired, USB port 1014and USB communication software 1013 may also be used as method ofconnecting INC 1010 to a personal computer. INC 1010 also includescamera interface module 1012, which may be software that providesfunction-based access (e.g. via an application program interface, orAPI) to various camera functions. These functions may includetransferring digital photographs from digital camera 1018, clearingmemory on digital camera 1018, taking a photograph using digital camera1018, changing configuration settings on digital camera 1018, or anyother suitable functions. INC 1010 also includes wireless transceiver1011. Using wireless transceiver 1011, one or more (e.g., any) other INCwithin the MPN can access the camera functions provided by camerainterface module 1012.

FIG. 10B shows INC 1020 that provides an interface to non-MPN MP3 player1028 with a USB port. INC 1020 includes USB port 1024, to which USBcable 1026 may be connected. The other end of USB cable 1026 may beconnected to MP3 player 1028. If desired, USB cable 1026 may be zerolength, i.e. INC 1020 may connect directly to MP3 player 1028. INC 1020includes USB communication software 1023 that provides the USBprotocols. If desired, USB port 1024 and USB communication software 1023may also be used as method of connecting INC 1020 to a personalcomputer. INC 1020 also includes music playback module 1022, which maybe software that provides function-based access (e.g. via an API) tovarious MP3 player functions. These functions may include transferringsongs to MP3 player 1028, clearing memory on MP3 player 1028, playingback a song or set of songs using MP3 player 1028, changingconfiguration settings on MP3 player 1028, or any other suitablefunctions. INC 1020 also includes wireless transceiver 1021. Usingwireless transceiver 1021, one or more (e.g., any) other INCs within theMPN can access the MP3 player functions provided by music playbackmodule 1022.

FIG. 10C shows INC 1030 that provides an interface to non-MPN mobiletelephone 1038 with an accessory port. INC 1030 includes accessory port1034, to which telephone accessory cable 1036 may be connected. Theother end of telephone accessory cable 1036 may be connected to mobiletelephone 1038. If desired, telephone accessory cable 1036 may be zerolength, i.e. INC 1030 may connect directly to mobile telephone 1038. INC1030 includes telephone communication software 1033 that provides theprotocols to communicate with mobile telephone 1038. INC 1030 alsoincludes telephone interface module 1032, which may be software thatprovides function-based access (e.g. via an API) to various mobiletelephone functions. These functions may include transferring phonenumbers to mobile telephone 1038, making a call on mobile telephone1038, adjusting the volume on mobile telephone 1038, changingconfiguration settings on mobile telephone 1038, or any other suitablefunctions. INC 1030 also includes wireless transceiver 1031. Usingwireless transceiver 1031, one or more (e.g., any) other INCs within theMPN can access the mobile telephone functions provided by telephoneinterface module 1032.

FIG. 10D shows INC 1040 that provides an interface to non-MPN PDA 1048with a wired synchronization port, for example a serial port or a USBport. INC 1040 includes synchronization port 1044, to whichsynchronization cable 1046 may be connected. The other end ofsynchronization cable 1046 may be connected to PDA 1048. If desired,synchronization cable 1046 may be zero length, i.e. INC 1040 may connectdirectly to PDA 1048. INC 1040 includes PDA communication software 1043that provides the protocols to communicate with PDA 1048. INC 1040 alsoincludes PDA interface module 1042, which may be software that providesfunction-based access (e.g. via an API) to various PDA functions. Thesefunctions may include transferring contact information to/from PDA 1048,transferring appointment information to/from PDA 1048, using PDA 1048 asan input device for other MPN functions, using PDA 1048 as a displaydevice for any other MPN functions, or any other suitable functions. INC1040 also includes wireless transceiver 1041. Using wireless transceiver1041, one or more (e.g., any) other INCs within the MPN can access thePDA functions provided by PDA interface module 1042.

FIG. 10E shows INC 1050 that provides an interface to non-MPN PDA 1058with an infrared communication port. INC 1050 includes infraredtransceiver 1054. A wireless infrared connection 1056 may be madebetween PDA 1058 and INC 1050, by directing the transceiver on each unitin the direction of the other. INC 1050 includes IR communicationsoftware 1053 that provides the protocols to communicate with PDA 1058over IR communication path 1056. If desired, infrared transceiver 1054and IR communication software 1053 may also be used as method ofconnecting INC 1050 to a personal computer. INC 1050 also includes PDAinterface module 1052, which may be software that providesfunction-based access (e.g. via an API) to various PDA functions. Thesefunctions may include transferring contact information to/from PDA 1058,transferring appointment information to/from PDA 1058, using PDA 1058 asan input device for other MPN functions, using PDA 1058 as a displaydevice for any other MPN functions, or any other suitable functions. INC1050 also includes wireless transceiver 1051. Using wireless transceiver1051, one or more (e.g., any) other INCs within the MPN can access thePDA functions provided by PDA interface module 1052.

FIG. 11 shows flowchart 1100 of illustrative steps to integrate anon-MPN device into an MPN. All steps in flowchart 1100 are optional andmay be performed in any suitable order. In step 1110, a physicalconnection is provided between an INC in an MPN and a non-MPN device.The physical connection preferably makes use of a connection typealready supported by the non-MPN device. The physical connection may bewired or wireless. For example, it may be USB, serial port, IR,accessory port, synchronization port, or any other suitable existingconnection. If desired, the physical connection may be the same as thewireless connection used to communicate between INCs in the MPN, if thenon-MPN device supports wireless communications, for example, if it is aBluetooth device. In step 1120, software is provided in the INC tocommunicate using the physical connection to the non-MPN device. Thissoftware may provide one or more protocol layers. It may include, forexample, USB drivers, IR drivers, or drivers to interface with aproprietary accessory port or synchronization port. If desired, thephysical connection provided in step 1110 and/or the communicationsoftware provided in step 1120 may also be used for other purposes bythe INC, such as to communicate with a personal computer.

In step 1130, a software interface may be provided in the INC to accessfunctions of the non-MPN device. For example, an API may provide amessage-based or function-based interface to any suitable subset offunctions implemented in the non-MPN device. If desired, the functionsprovided need not map one-to-one to functions provided by the non-MPNdevice. In step 1140, other INCs in the MPN are allowed to access thefunctions of the non-MPN device. For example, a command may be sent byanother INC and received by the interfacing INC. The received commandmay map onto a function from the device API. The interfacing INC maysend one or more commands and/or data to the non-MPN device, which mayin turn return results and/or data. The interfacing INC may then returnthe appropriate results, which may be derived from the results providedfrom the non-MPN device, to the other INC.

Every MPN is unique, and has a unique set of capabilities, depending onthe needs of the individual user. The user can modify the MPN at anytime depending on the needs of the day or hour, or the specific occasionor event. It is simple to add or remove one or more INCs at any time.FIGS. 12 and 13 show block diagrams of example individual MPNs.

FIG. 12 shows a block diagram of example MPN 1200. MPN 1200 includescontrol unit 1210. Control unit 1210 can be considered thegeneral-purpose processor for controlling the functions of MPN 1200. Itincludes a microprocessor and memory. The memory can be used fordownloading software modules to control the other INCs and to performother specific functions. It can also be used for collecting data fromthe other INCs. Memory can be of any type or combination of types, suchas RAM, hard disk. CD-ROM, mini-disk, or flash memory, and may bepermanent or removable. Control unit 1210 may be worn on the user'swaist, worn on a wristband, carried in a pocket or purse, or carried orworn in any other suitable manner. If desired, functions of control unit1210 may be combined into a single INC with other functions, such asdisplay and user input functions.

Display device 1220 may typically be a general-purpose graphical oralphanumeric display, such as a liquid crystal display, or LCD. It may,for example, be worn on the wrist. Audio output device 1230 may includeone or more speakers to output music, audio status information,generated speech, or any other audio content. It may also includedigital-to-analog converters and amplifiers to generate an appropriateaudio signal to output. It may be worn in the form of a set ofheadphones, a single ear bud, a speaker that is attached to a hat orheadband, or any other suitable form. It may also be in the form of aspeaker embedded into another INC.

User input device 1240 may include one or more of any suitable type ofuser input. This may include one or more buttons, a microphone withspeech recognition, pen-based input, a keyboard, or any otherappropriate portable user input device. User input device 1240 may beworn on the hand or wrist, attached to a set of headphones, worn at thewaist, or worn or carried in any other suitable manner. User inputcontrols, such as buttons, may also be incorporated into any other INC,such as a display device or control unit.

Mobile telephone interface 1250 may make the functions of the user'snon-MPN mobile telephone available to the other INCs in MPN 1200, asdescribed above with respect to FIG. 10C. Mobile telephone interface1250 may be designed to be worn on the waist or carried in a pocket orpurse, or otherwise carried or worn. The functions of mobile telephoneinterface 1250 may also be included in another INC, such as a controlunit.

Location monitor 1260 may include a global positioning system (GPS)receiver and antenna, to provide current location and speed informationto the other INCs in MPN 1200. It may be designed to be worn on anarmband or a waistband, or otherwise to be worn or carried. If desired,the GPS antenna may be separate from the GPS receiver. If desired, thefunctions of location monitor 1260 may be integrated into another INC,such as control unit 1210, or mobile telephone interface 1250.

The INCs in MPN 1200 communicate over wireless communication path 1290.This includes sending commands, responses, data, information, audio tobe output, information to be displayed, user input commands, mobiletelephone commands, position and speed information, and any othersuitable messages.

FIG. 13 shows a block diagram of another MPN 1300. MPN 1300 is differentfrom MPN 1200 in that it does not include a control unit. Instead,control is distributed among the INCs in MPN 1300. Each INC provides itsfunctions to the other INCs independently. Display device 1320, audiooutput device 1330, and user input device 1340 are similar to INCs 1220,1230, and 1240, respectively, as described previously in conjunctionwith FIG. 12.

Storage device 1310 includes memory that can be used by the other INCsin MPN 1300. Memory can be of any suitable form, such as RAM, flashmemory, mini-disk, etc., and may be permanent or removable. Data, suchas digital music files, can be loaded into storage device 1310 from apersonal computer. Data may be sent from storage device 1310 to otherINCs, such as audio output device 1330. In that example, music may begenerated from the music files and output using audio output device1330. Data may be sent by other INCs, such as digital camera interface1350 and heart rate sensor 1360 and stored by storage device 1310. Thedata collected by storage device 1310 may later be sent to a personalcomputer. Storage device 1310 may be worn on the user's waist, worn on awristband, carried in a pocket or purse, or carried or worn in any othersuitable manner. If desired, functions of storage device 1310 may becombined into a single INC with other functions, such as display anduser input functions.

Digital camera interface 1350 may make the functions of the user'snon-MPN digital camera available to the other INCs in MPN 1300, asdescribed above with respect to FIG. 10A. Digital camera interface 1350may be designed to be worn on the waist or carried in a pocket or purse,or otherwise carried or worn. The functions of digital camera interface1250 may also be included in another INC, such as a storage device.

Heart rate sensor 1360 may include a sensor to measure heartbeats. Itmay be designed to be worn on a chest strap.

The INCs in MPN 1300 communicate over wireless communication path 1390.This includes sending commands, responses, data, information, music andother audio to be output, information to be displayed, user inputcommands, digital camera commands, digital images, heart rate data, andany other suitable messages.

INC 1200 and INC 1300 are shown purely by way of illustration. A usermay configure any suitable combination of INCs into an MPN. A user mayalso change which INCs are included in an MPN at different times, basedon specific circumstances, needs, mood, or any other factors.

A user can purchase MPN components in any suitable package from anymanufacturer. If desired, INCs from different manufacturers can be mixedwithin a single MPN. If desired, an INC from one manufacturer can bereplaced by an INC from another manufacturer.

FIG. 14 shows flowchart 1400 of steps that may be performed to providevarious packages of MPN components and related product items. Some ofthe steps in flowchart 1400 are optional and may be performed in anysuitable order. In step 1410, a starter kit may be provided. The starterkit may include an application that can be loaded onto a PC to controland configure the MPN. It may include a security lock value, asdiscussed above in conjunction with FIG. 3. It may include one or morebasic INCs, such as a control unit, a display device, etc. It mayinclude a PC connection cable or docking station. It may include a linkto a website to find updated plug-ins for the PC control application,device drivers, device lists, etc. It may include one or more userinstruction manuals. It may also include coupons for other MPN productsoffered by the same manufacturer. It may include any other suitableitems.

In step 1420, a device kit may be offered. This kit includes a specificINC. It may also include a plug-in for the PC application to configurethe INC, a device driver to be downloaded to the device or to a controlunit, a PC connection cable or docking station, a link to a website forupdates, one or more instruction manuals, or any other suitable items.

In step 1430, a multi-purpose device kit may be provided. This may besimilar to the device kit provided in step 1420, with the addition thatthe single INC may provide multiple features.

In step 1440, a feature kit may be provided. The feature kit includesall items necessary to add a specific feature to an MPN. This mayinclude one or more INCs (if the feature cannot be implemented usingexisting INCs). It may include a plug-in for the PC application. It mayinclude one or more device drivers to be downloaded into INCs in theMPN. It may include one or more cables. It may also include a link to awebsite for updates, an instruction manual, and any other suitableitems.

In step 1450, an adaptor kit may be offered. The adaptor kit may includean INC that is configured to communicate with a non-MPN device, asdescribed above in conjunction with FIG. 11. The kit may include one ormore adaptor cables (each cable configured for a specific subset ofnon-MPN devices), a plug-in for the PC application, device drivers, awebsite link for updates, an instruction manual, and any other suitableitems.

Each MPN can perform many functions, depending on the componentsincluded by its user and depending on the software and configurationparameters loaded. Some of the most common functions may include timekeeping functions (such as current time, stop watch functions, etc.),personal organizer functions (such as contact management and appointmentnotification), music playback, and games.

If desired, an INC in one MPN can communicate with an INC in anotherMPN, when the users are in close proximity. When a message is sent froman INC, it may be tagged with an identification of the MPN in which itoriginated. An INC can use this information to generate a message thatis targeted for an INC in the other MPN. This can be used, for example,to allow two or more users to play a multi-user game or participate inany other type of multi-user competition. Each user may use his or herown input device, display, and audio output, and information related tothe game or competition may be sent in messages between the INCs in theMPNs.

MPN users can also exchange other types of data. For example, a user ofone MPN can send software, which may be control software for an INC inthe MPN, to the user of another MPN. A user of one MPN can send personalinformation, such as contact information, to a user of another MPN. Auser of one MPN can send media files, such as digital music files anddigital photographs, to a user of another MPN.

Another example of information exchange between MPNs is betweenmusicians. A musician may have an MPN with INCs designed to supportmusic-related functions. For example, the musician may have one or moreINCs that include microphones, one or more INCs that include speakers,an INC that has memory to store music (e.g., as sheet music, as digitalaudio files, or in any other suitable format), an INC that can convertmusic from one format (e.g., Midi) to another (e.g., MP3) for output, anINC to perform audio processing and other special effects, an INC to mixmultiple inputs, an INC to display sheet music, and any other suitablefunctions. If desired, an INC can support multiple music-relatedfunctions. If desired, the musician's MPN may include INCs that are usedfor non-music-related functions.

FIG. 15 shows a block diagram of two MPNs that may be used by twomusicians to collaborate in music-related activities. Only two MPNs areshown for simplicity, although more than two musicians can easily usetheir MPNs to collaborate in music. The INCs shown are illustrative, andmay vary from MPN to MPN.

Music collaboration system 1500 includes MPN 1520 and MPN 1540. Thecomponents of each MPN are associated with a single user, and may bewom, carried, or in close proximity to that user. When the users of thetwo MPNs are in close proximity to each other, the INCs in their MPNsmay send messages and music collaboration is made possible.

MPN 1520 includes INC 1521, which may be a control unit. Control unit1521 may include a processor for performing music-related processing,and memory for storing music-related data. For example, it may storesheet music files, Midi files, MP3 files, or any other type of musicfiles. It may perform music-related functions, such as special effects,gain control, format conversion, mixing of multiple inputs, or any othersuitable music or audio processing functions. INC 1522 may include amicrophone. If desired, MPN 1520 may include multiple microphone INCs,or other INCs to provide for input of audio signals, for exampledirectly from musical instruments. INC 1523 may include input controls.These may include, for example, buttons, a computer-type keyboard, amusic-type keyboard, a touch screen interface, knob or level type analoginputs, or any other suitable type of input device. Multiple inputdevices may be included. INC 1524 may include a speaker and amplifier.If desired, multiple speaker INCs may be provided. INC 1525 may be adisplay device.

The second musician's MPN 1540 may be similar, and the selection of INCsmay vary. In this example, MPN 1540 includes control unit 1541,microphone 1542, input controls 1543, and display device 1545, similarto INC 1521, INC 1542, INC 1543, and INC 1545, respectively. In thisexample, the second MPN does not include a speaker.

Some of the features of the music collaboration system include messagessent between the individual MPNs over wireless communication path 1560to coordinate the timing and playing of a single piece of music. Thedisplays of each MPN can show the same piece of music, or the relevantpart of the same piece of music. Timing signals, such a metronomepulses, can be sent to an audio or display device for each musician.Timing signals may also be displayed directly on the sheet music.Multiple audio inputs, received by INCs in multiple MPNs, can be mixedand stored by an INC in one of the MPNs, as well as played on speakersthat are part of one or more of the MPNs. The recorded music can laterbe uploaded to a PC or other music processing system for laterprocessing. The music generated by the multiple musicians can beprocessed within any of the MPNs.

FIG. 16 shows a block diagram of another illustrative MPN configuration1600. MPN 1600 may be configured to provide mobile wildlife recognitionand logging. Note that MPN 1600 may also be used for other purposes,such as mobile recognition of other objects, as an electronic journal,or any other suitable purpose. INC 1621 is a control unit. It mayinclude a processor, memory, and a clock. INC 1622 is a digital camera.It may alternatively be an INC configured to interface with a non-MPNdigital camera, as described above in conjunction with FIG. 10A. INC1623 is an audio input device. It may includes a microphone and ananalog-to-digital converter. It may be used for capture of externalaudio samples, as well as for input of user voice commands. INC 1624 maybe a user input device. If desired, INC 1623 may be used as a user inputdevice. If desired, user input may be provided with any suitablecombination of keyboard, buttons, pen-based input, touch screen, or anysuitable other device. If desired, multiple user input INCs may beincluded INC 1625 may be a location monitor, and may include a GPSreceiver and antenna. INC 1626 may be a display device. INC 1627 may bean audio output device. The INCs in MPN 1600 communicate over wirelesscommunication path 1629.

The configuration shown in FIG. 16 is merely illustrative. Other INCsmay be included if desired. Some INCs may be omitted. If desired,functions of multiple INCs may be combined into a single device.

FIG. 17 shows illustrative flowchart 1700 of a process that may be usedto provide mobile wildlife recognition and logging of individualsightings. All steps in flowchart 1700 are optional and may be performedin any suitable order. In step 1710, a library of information aboutlocal flora and/or fauna may be downloaded into memory on one of theINCs, such as control unit 1621. The library may be downloaded from apersonal computer. The library may have been loaded on the personalcomputer over the Internet, or using a removable storage device such asa CD-ROM or DVD-ROM. If desired, INC 1621 may be configured to use aremovable storage device, such as a flash memory card or mini-disk, andthe library may be loaded onto the removable storage device. The librarymay be related to flora and fauna that may be found in a particularregion that the user may be planning to visit. It may include digitalimages, audio samples of animal calls, information about habits andterritories, text descriptions, and any other suitable information.

In step 1715, the user may be allowed to capture an image (or multipleimages) at a sighting, which may be of an animal or plant or othersuitable object. The user may use digital camera INC 1622, and thecaptured image may be stored in memory on one of the INCs, such ascontrol unit 1621. If desired, the user may also capture one or moreaudio samples in step 1720. The audio sample may be, for example, thecall of the animal of which the image was capture. Other relevantinformation may also be captured in step 1725, and stored into memory incontrol unit 1621. This may include logging the current day and time,which may be done using the clock which is part of control unit 1621. Itmay also include the current location, which may be captured by locationmonitor 1625. Any other suitable information may also be captured andstored into memory in control unit 1621. This may include, for example,the current weather conditions. It may also include information enteredby the user on user input device 1624. For example, the user may enternotes about the activities of the animal, the environment, or any othernotes of interest.

In step 1730, the system may determine likely matches between thecaptured image and the items in the downloaded library. This may be doneby comparing the captured image to the images in the library, comparingthe captured audio sample to the audio samples in the library, comparingthe captured time and location to information about the habits of theitems in the library, or using any other comparisons. Any of thesecomparisons may also be done in combination. The processor in controlunit 1621 may perform the comparisons. Based on the results of thesecomparisons, one or more of the most likely matches may be chosen. Instep 1735, the most likely matches may be presented to the user. Thismay include displaying one or more images from the library for eachmatch on display device 1626. It may also include playing audio samples,such as animal calls, from the library on audio output device 1627.Other information related to the matched items from the library may alsobe presented to the user, for example on display device 1626. In step1740, the user may be allowed to choose one or more of the likelymatches, or to rank the likely matches, or to exclude one or more of thelikely matches using user input device 1624.

In step 1745, the system may maintain a log, for example in memory incontrol unit 1621, of each sighting. Each log entry includes all of thecaptured images, all of the captured audio samples, the time andlocation stamp of the sighting, current weather conditions if available,any additional information entered by the user, and the results of thematch, including the user determination or ranking. In step 1750, theuser may be allowed to view past log entries, including all of therelated data, captured images, and captured audio samples. The user mayalso be able to augment the notes or refine the match. In step 1755, theuser may be allowed to upload all of the information from the log to apersonal computer. This may include converting the various items of datato suitable formats for viewing and processing on the personal computer.For example, the personal computer may create or augment a databasefile, with links to image files (e.g., JPEG) and audio files (e.g.,MP3). Software on the personal computer may allow the user to view andedit the log. There may also be an Internet interface that allowsmultiple users to upload log entries and share and compare them. In step1760, the log entries may be shared between the MPN and another MPN thatmay have similar features. For example, two naturalists, each with hisor her own wildlife recognition and logging system, may swap sightinglogs. In this case, each log entry may also be automatically tagged withthe identification of the person who made the sighting.

Each INC is designed to function in close proximity to the user of theMPN. An INC may have means to wear or carry 670, as shown in FIG. 6.There are many examples of how any particular INC can be designed toprovide means to wear or carry 670. Illustrative methods for designingINCs to be carried or worn are shown in flowchart 1800 of FIG. 18. Allsteps in flowchart 1800 are optional and may be performed in anysuitable order.

In step 1810, some INCs may be designed to be carried in a pocket orpurse. In this case, there may not be a specific means to wear. However,the INC may be designed in a manner so that its functions are notdisturbed by jostling that may occur when carried in this manner.

In step 1820, some INCs may be designed to be attached to a piece ofequipment that is in close proximity to the user of the MPN. Forexample, the INC may be attached to a piece of exercise equipment (e.g.,a treadmill), to a bicycle, to a car, or to a wheelchair. It may also bemounted on an item of furniture, such as a bed or chair.

In step 1830, some INCs may be embedded into another piece of equipment.For example, an item of medical equipment that may be carried by adoctor or therapist, or may be used by a doctor or therapist, may act asan INC in the doctor's or therapist's MPN, or in the patient's MPN.

In step 1840, some INCs may be designed to be worn directly by the user,or may have attachment means to allow them to be worn directly. Forexample, an INC may have a wristband or a waistband. Some INCs may bedesigned to be mounted on a special item of clothing that is worn by theuser. For example, an INC may be mounted to a special glove or headbandthat is designed specifically to facilitate the mounting of INCs.

In step 1850, some INC may be designed to be attached to a user'sexisting clothing. For example, an INC may be help in place by the fitof an item of clothing, or it may be attached to the clothing usingmeans such as a pin, a hook and loop fastener, or any other suitablemeans.

In step 1860, some INCs may be designed to be carried internally to theuser's body. These INCs may, for example, be injected into the user'sblood stream, ingested by the user, or implanted into the user's body.

In step 1870, some INCs may be designed as items of jewelry. As jewelryitems, they may mount directly on the body, or they may attach toclothing worn by the user. These jewelry INCs may be designed to looklike jewelry, hiding the appearance of being an electronic device, aswell as being designed for aesthetic enjoyment. Any of these INCs mayinclude one or more precious, semi-precious, or costume stones, acrafted design, real or imitation precious metals, or any othercomponents to enhance the aesthetic value of the INC.

Flowchart 1870 of FIG. 19 shows more detailed illustrative methods fordesigning INCs to be worn as items of jewelry. All steps in flowchart1870 are optional and may be performed in any suitable order.

In step 1910, an INC may be configured as an earring, or other type ofbody jewelry designed to be worn in a pierced body part. A pair ofearring INCs may perform complementary functions. One example of anearring INC may include a wireless receiver and a speaker. Two such INCsmay function as a pair, providing stereo outputs. These INCs allow otherINCs to send audio content to be played in close proximity to the user'sear, at a low and unobtrusive volume. Another example of an earring INCmay include an antenna for a GPS receiver or a mobile telephone or othercommunications device. The received signal may be remodulated and sentto another INC for processing. These are merely examples, and any othersuitable function may be performed by an earring INC. An INC may also beincorporated into an item of body jewelry designed to be worn in anyother pierced body part, such as nose, tongue, nipple, etc.

In step 1915, an INC may be configured as a necklace or pendant. Apendant, for example, may be any appropriate INC, such as a controlunit, a display device, a user input device, a GPS receiver, or anyother suitable function or combination of functions. If the INC isconfigured as a necklace, the electronic components may be incorporatedinto a specific portion or segment of the necklace, or they may bedistributed about the necklace.

In step 1920, an INC may be configured as a ring. Examples of suitablering INCs may include a user input device, such as a push button or amicrophone. Any other type of suitable device may be implemented as aring INC, such as a digital camera, a pulse oximeter, a heart ratesensor, a blood pressure sensor, a simple display device, etc.

In step 1925, an INC may be configured as a bracelet or as an anklebracelet, or as similar jewelry to be worn around any other part of thebody. With this type of INC, the electronic components may beincorporated into a specific portion or segment of the band, or they maybe distributed about the band.

In step 1930, an INC may be configured as a barrette, a hairpin, or anyother type of hair accessory, such as a hair band. An antenna would bean example of a suitable function to incorporate into this type of INC.In step 1935, an INC may be configured as a pin or brooch. In step 1940,an INC may be configured as cuff links, a tie tack, a tuxedo stud, orother similar item. An INC with any suitable function may be attached tothe clothing in such a manner, such as a communication device, a userinput device, etc.

In step 1945, an INC may be incorporated into a pair of eyeglasses. Forexample, the temple of the eyeglasses may incorporate an antenna or aspeaker. In step 1950, an INC may be configured as a belt buckle. Forexample, such an INC may include a user input device.

These steps are merely illustrative of the types of INC jewelry that maybe created. An INC may be configured as any type of jewelry, and mayincorporate any suitable function. The function chosen for a particularINC may be based on the size of the item of jewelry and on the locationon the body on which it is worn.

FIG. 20 shows an illustrative user with a jewelry-based MPN 2000. INCs2010 are earring-based INCs, and may incorporate speakers. INC 2020 is ahair band INC, and may incorporate a mobile telephone antenna. INC 2030is a pendant-based INC, and may incorporate a microphone. INC 2040 is abrooch INC, and may incorporate a processor and memory, and may operateas a control unit. INC 2050 is a bracelet INC, and may include a userinput device (such as a numeric key input). INC 2060 is a ring-basedINC, and may include a separate user input device. As an example, MPN2000 may provide a mobile communication system to the user, along withother functions. The types of jewelry and the functions provided aremerely illustrative. Any suitable INCs can be provided and they mayprovide any suitable combination of functions. If desired, an MPN thatincorporates jewelry-based INCs can also incorporate other types of INCsthat are not jewelry-based.

A single item of jewelry can include multiple modules, which can beindividually added, removed, or replaced. A charm bracelet allows theuser to add multiple charms. A modular bracelet may allow the user toadd or replace individual links. Similarly, a modular necklace or anklebracelet may allow the user to add and replace individual links.

Each link or charm may act as a separate INC in an MPN. A single jewelryitem can contain many INCs, each of which may provide a differentfunction. If desired, multiple modules may provide similar functions,such as memory. As an example, one link in a modular bracelet may act asa control unit, several may provide additional memory, one may providean input sensor (e.g., a temperature sensor or a heart rate sensor), andone may provide a user input device.

If desired, the entire item of jewelry may act as a single INC. Forexample, one of the modules may provide the wireless transceiver used byall of the other modules to communicate within the MPN. Alternatively,the base jewelry item (e.g., the modular bracelet without any addedlinks) may provide basic INC functionality. For example, the braceletmay include a wireless transceiver, a PC connection, a processor andother control circuitry, memory, power, and security-processingcircuitry. Each added jewelry module may include only the electronicnecessary to add a specific function, along with any desired aestheticfeatures. The base jewelry system may act as a communication and powerbus for transferring data and power among the jewelry modules in thesystem.

FIG. 21 shows a block diagram of illustrative modular jewelry system2100. Bracelet 2110 provides the base unit to which the jewelry modulesare added. It includes power and communication bus 2115, which may beused to carry power to each of the internal subsystems (2125, 2130,2135, 2140, and 2145) in the bracelet as well as to the added modules(e.g., modules 2160 and 2165). Bus 2115 also carries data among theinternal subsystems and added modules.

Power subsystem 2120 provides power to the bracelet, both the internalsubsystems and any added modules. It may be similar to power module 660shown in FIG. 7. Security-processing subsystem 2125 provides securityfeatures for the modules added to the system. In addition, each modulemay include its own security-processing subsystem. Security-processingsubsystem 2125 may be similar to security-processing circuitry 543discussed in conjunction with FIG. 5. Wireless transceiver 2130 provideswireless communication between the bracelet (any of its internalsubsystems or added modules) and any external INCs. Memory 2135 providesstorage of any appropriate type (e.g., RAM, ROM, or flash memory). Itmay be used by the internal subsystems as well as by any of the addedmodules. Control subsystem 2140 may include a processor. It may alsoinclude any other circuitry suitable for controlling the internalsubsystems, for controlling the added modules, for coordinating datasent between and among subsystems and modules, and any other suitablefunction. PC connection subsystem 2145 may provide hardware and softwareto interface the modular jewelry system with a personal computer. It maybe similar to PC connection 620 described in conjunction with FIG. 6.

Modular jewelry system 2100 may include multiple module connections2150. Each connection 2150 provides the physical attachment means forattaching a module to the base unit. Each connection 2150 also providesthe electrical connection between the added module and power andcommunication bus 2115. Preferably, connection 2150 is designed to astandard physical and electrical specification, which is published tomanufacturers of individual modules. Each module is preferablymanufactured to the same specification, so that any module isinterchangeable with any connection on any base system. In addition, thestandard specification may detail a communications protocol by whichindividual modules may make their capabilities available and may takeadvantage of the capabilities of other subsystems and modules. Modules2160 and 2165 are examples of jewelry modules added to modular jewelrysystem 2100. They may provide any suitable functions or combination offunctions. Each module may include its own aesthetic design, or themodules may share a common design.

If desired, bracelet 2110 may include any suitable additional functionsas internal subsystems, so that they do not need to be added as modules.The internal subsystems shown are merely illustrative and may vary.Although a modular bracelet is shown in this example, any other suitabletype of modular jewelry may be used in this system, such as a charmbracelet, a modular necklace, a modular ankle bracelet, or a modularbelt.

If desired, modular jewelry system 2100 may function as a standaloneunit and network, rather than functioning as a component in a modularpersonal network. In this case, wireless transceiver 2130 need not beincluded. In this type of network, functions are added, removed, orchanged by adding, removing, or replacing individual jewelry modules. Inaddition, functions of the modular jewelry system may be changed bydownloading different software using PC connection 2145. Software can bedownloaded into an internal subsystem (such as memory 2135) or into anadded module, such as module 2160.

FIG. 22 shows flowchart 2200 of an illustrative process for providing amodular jewelry system. All steps are optional and may be performed inany suitable order. In step 2210, a base unit may be provided. The baseunit may be, for example, a modular bracelet, a charm bracelet, amodular necklace, a modular ankle bracelet, a modular belt, or any othersuitable type of unit. In step 2215, the base unit may include power anda power bus for distributing the power among internal and externalcomponents. In step 2220, the base unit may include communication busfor distributing data among internal and external components. In step2225, the base unit may include multiple standard connections forattaching jewelry modules. Each connection may be manufactured to astandard specification to provide a physical connection to the baseunit, an electrical connection to the power bus, and an electricalconnection to the communication bus. In step 2230, the base unit mayinclude common control circuitry. This may include a processor, memoryof any suitable type, and any other circuitry for supporting theinternal and external components. In step 2235, the base unit mayinclude security circuitry. This circuitry may interface with securitycircuitry in added modules to ensure that, once a module has beenidentified as belonging to a specific system, it cannot be moved toanother modular jewelry system without user authorization. It may alsofunction to ensure that the base unit itself cannot be used in adifferent MPN once it has been configured by a particular user. In step2240, a PC connection may be provided. This may allow information to besent from a personal computer to the base unit or any attached modules,as well as allowing information to be sent from the base unit and anymodules to a personal computer. This may include software, data,configuration information, or any other suitable information. In step2245, external communication may be provided by the base unit. This mayinclude, for example, a wireless transceiver as well as suitablesoftware and hardware protocols. In step 2250, a variety of modules maybe provided to be added to the modular jewelry system. Each may conformto the physical, electrical, and protocol specifications published tomanufacturers of such modules. Each module may provide one or moresuitable functions to the system. Each may include its own securitycircuitry to ensure that it cannot be misused once it has beenconfigured for a specific user and modular jewelry system.

A circuit or circuitry for implementing different techniques orfunctionality illustratively described herein may comprise hardware(e.g., discrete electronic circuit components), software, or acombination thereof configured to provide such techniques or functions.

Thus, we have provided systems and methods for improvements to a modularpersonal network. One skilled in the art will appreciate that thepresent invention can be practiced by other than the describedembodiments, which are presented for the purposes of illustration andnot of limitation. Other embodiments are possible, including other uses,functions, components, and combinations thereof. The present inventionis limited only be the claims that follow.

1-9. (canceled)
 10. A personal performance monitoring system configuredto be worn by a user comprising: a first item of jewelry having aprocessor, a memory operatively coupled to the processor, a wirelesswide area network transceiver, and a first personal area networktransceiver, wherein the first item of jewelry is configured as acontrol unit for a wireless personal area network; and a second item ofjewelry having a second personal area network transceiver and a sensorconfigured to sense performance data of the user, wherein the first itemof jewelry is configured to wirelessly communicate via its firstpersonal area network transceiver with the second item of jewelry viaits second personal area network transceiver over the wireless personalarea network.
 11. The system of claim 10, wherein at least one of thefirst and second items of jewelry is configured to be worn by directlymounting on the body.
 12. The system of claim 10, wherein one of thefirst and second items of jewelry is configured to be worn by attachingto an article of clothing worn by the user.
 13. The system of claim 10,wherein one of the first and second items of jewelry comprises one of abrooch, a cufflink, a tie tack, a tuxedo stud, a barrette, a hairaccessory, a necklace, a bracelet, an earring, a watch, a ring, andeyeglasses.
 14. The system of claim 10, wherein the first item ofjewelry is configured to communicate with a remote computer through thewireless wide area network transceiver.
 15. The system of claim 10,wherein the first and second items of jewelry are configured to appearas typical items of jewelry by hiding an appearance of being anelectronic device.
 16. The system of claim 10, further comprising anadditional component configured to wirelessly communicate with the firstand second items of jewelry over the personal area network, wherein theadditional component is a non-jewelry component.
 17. The system of claim10, further comprising a third item of jewelry configured to provide anoutput to the user.
 18. The system of claim 17, wherein the outputcomprises an audio output.
 19. The system of claim 17, wherein theoutput comprises a visual output.
 20. The system of claim 17, whereinthe output is based on the performance data received by the sensor. 21.The system of claim 17, wherein the output is based on communicationfrom the first item of jewelry.
 22. The system of claim 10, furthercomprising a third item of jewelry configured as an input device. 23.The system of claim 10, wherein the sensor comprises one of anaccelerometer, a gyroscope, a temperature sensor, a pulse oximeter, ablood pressure sensor, and a heart rate sensor.
 24. The system of claim10, wherein the performance data comprises one of location, speed, pace,elevation, steps taken, distance traveled, cadence, heart rate, andblood pressure.
 25. A personal performance monitoring modular jewelrysystem configured to be worn by a user comprising: a base item ofjewelry comprising a wireless transceiver, a processor, and a memoryoperatively connected to the processor; a plurality of moduleconnections disposed on the base item of jewelry; and a plurality ofjewelry modules configured to attach to the base item of jewelry at themodule connections.
 26. The system of claim 25, wherein each moduleconnection comprises a physical attachment and an electrical connection.27. The system of claim 25, wherein the base item of jewelry and theplurality of jewelry modules are configured to act together as a singlenetwork component of a personal area network.
 28. The system of claim25, wherein each jewelry module is configured to act as its own networkcomponent of a personal area network.
 29. The system of claim 25,wherein one of the jewelry modules provides an additional sensingfunction not provided by one of the base item of jewelry and another oneof the jewelry modules.
 30. The system of claim 25, wherein one of thejewelry modules provides increased capacity of an already existingfunction provided by one of the base item of jewelry and another one ofthe jewelry modules.
 31. The system of claim 25, wherein the base itemof jewelry comprises a communication and power bus configured totransfer data and power among the plurality of jewelry modules.
 32. Thesystem of claim 25, wherein any of the plurality of module connectionsare configured to receive any of the plurality of jewelry modules. 33.The system of claim 25, wherein the plurality of jewelry modules areconfigured to be interchangeable.